Release 10.1A: OpenEdge Application Server:
Administration

After deploying Web services

After deployment, in the Progress Explorer, you will notice an icon for the Web services under the Web Services folder for the WSA instance. Also, the files listed in Table 6–5 are created in the WSA instance directory.

Table 6–5: File created when a Web service is deployed

File	Description
friendlyname.props	An XML file containing the current Web service property settings (initially set from default.props).
friendlyname.wsad	The Web Service Application Descriptor (WSAD) XML file that defines the Web service to the WSA instance.
friendlyname.wsdl	The WSDL XML file that defines the Web service to potential Web service clients.

During development, you can change the definition and deployment information of a deployed Web service using a Web service update. You can use Progress Explorer or WSAMAN to do this. However, once deployed and enabled for client access under production conditions, avoid making any changes to this information, as client implementations depend on its stability.

To make the same Web service available using different information after production deployment (for example, to add a new operation or use a different SOAP Message Style), deploy a new Web service with the new information by using a different Web service name and target namespace at the same WSA instance (similar to versioning a Web service), or by deploying the Web service to a different WSA instance.

However, you can always change the run-time properties of a deployed Web service at any time, but most properties require that you first disable the Web service. For more information, see the Progress Explorer online help, Chapter 8, "Using the WSA Management Utility (WSAMAN)," Appendix B, "Command and Utility Reference," and Appendix A "Reference to Progress 4GL Web Service Properties."